Overview
Goose (Block’s autonomous developer agent) now supports direct remote HTTP endpoints for connecting to Civic MCP servers with full OAuth2 support.Prerequisites
Goose
Install Goose autonomous developer agent
Civic Account
Create a free account on nexus.civic.com
Setup with Remote HTTP Endpoint
Get your MCP URL
- Sign in to nexus.civic.com
- Select the MCP servers you want to use
- Copy the MCP URL:
https://nexus.civic.com/hub/mcp
Configure Goose
Add the Civic MCP server to your Goose configuration:
- Open your Goose configuration file (typically
~/.config/goose/config.yamlor project-specific.goose/config.yaml) - Add the following MCP server configuration:
Goose supports HTTP endpoints directly, no local bridge required.
Test Connection
Verify the connection is working:Goose should respond with the list of available Civic tools.
Authenticate Services
When you first use a tool that requires authentication:
- Goose will prompt you to authorize access
- A browser window will open for OAuth authentication
- Sign in to the service and authorize access
- Return to Goose when complete
Authentication is handled securely by Civic. Your credentials are never exposed to Goose or stored locally.
Alternative: Hub Bridge Setup
If you prefer to use the local Hub Bridge instead of direct HTTP endpoints:Resources
Client Compatibility
Goose MCP support details (Remote URL method)
Claude Desktop Guide
Similar Remote URL setup process
Troubleshooting
Common connection issues
Get Help
Join our developer community for Goose setup help

